Star Trek Campaigns - Brentanus-Cafu War
Scenario 11 - The Chase To Bowman's Star


Game Master Notes- Part 2

Scenario 11, prepared by David Ternes


The "Real" Story.

Much is not as it was stated in the Federation and Klingon presentations. Everything in the Klingon information for "Tublar's Battle Fleet" is correct. Most of the Federation information for "Task Force 372" is correct. Little of the Klingon information for "Singger's Raiding Group" is correct.

Singger's Raiding Group. This is a Star Fleet unit! It is officially known as Task Force K1. In the past few months Star Fleet has captured a number of Klingon warships. Sector command has obtained the use of four of these ships for the attack on Bowman's Star. The plan is simple. Task Force 372 will "pursue" Task Force K1 which will be composed of the four ex-Klingon ships with specially trained Star Fleet personnel impersonating the Klingon ship command personnel. Task Force K1 will "run" towards the Bowman's Star system and call for help, reporting that they are the remains of "Singger's Raiding Group" (a unit which existed and was destroyed while out raiding). Once Task Force K1 has joined the Klingon battle group defending Bowman's Star, they will have two objectives. First they will attempt to land Federation Marines on the research station to capture it. Second, they will wait for the most opportune moment and attack the Klingon forces from behind, in support of Task Force 372's attack.

Task Force 372 did not react to the entry of a Klingon raiding group into its system. Rather, that is the history loaded into the memory banks of the ships in Singger's Raiding Group, and the story which that group will tell, if asked. Both Task Force 372 and Task Force K1 are acting out their parts in the charade which will, hopefully, get Task Force K1 into the desired position.

Singger's Ships. The information about the ships in Singger's Raiding Group is correct, with the following modifications.

Locking-On. Prior to revealing their true identity, ships in Singger's Raiding Group may attempt to lock-on to Klingon ships. The roll should be made in secret, or made as if trying to lock-on to a Federation vessel. If they fail to achieve the lock, nothing happens. If they get a lock, the targeted Klingon vessel should be informed, at the end of the Lock-On Phase, that it detects unusual scanning activity, and that it has just been scanned.

Dropping The Charade. Once the Task Force K1 opens fire, all pretext of working with or being Klingons must be dropped, and the unit acts like a Federation force.

Special Communications. Impersonating Klingons will require some role playing on the part of the ships commanders in Singger's unit. However, if done too well, the Klingons may have no chance of realizing their situation. Therefore, some of the responses by Singger to Klingon queries have been scripted below. If a communication does not fall within the following requirements, then Singger may respond as desired. The Queries should be liberally interpreted (i.e., every possibility should be considered so as to cause Singger to use the following Answers). This rule is optional, and the game master is free to required their use or ignore them.


Communications Between "Klingon" Forces.

Each time the Klingons attempt to communicate with Singger's Raiding Group, the game master should roll a D10 and consult the following table. The attempt may be made at the start of the game and once after each Sensor Phase. This communication does not count as a Sensor Question.

If communication is possible and the communication falls into one of the categories on Singger's Raiding Group's communications list, then the commander of the force should reply as indicated.

The use of this rule is optional. It may be needed if the Klingon players are too dense to realize that Singger's unit is not acting as they would expect a Klingon unit to react. With perceptive players, this is almost sure to trip their suspicions early in the game.


Back To the Top of the Scenario      Back To Game Master Notes Part 1